Skip to content

[release-4.20] OCPBUGS-81484: CUDN: cleanup NADs in terminating namespaces without pods#3102

Open
kyrtapz wants to merge 1 commit into
openshift:release-4.20from
kyrtapz:cudn_ns_cleanup_fix
Open

[release-4.20] OCPBUGS-81484: CUDN: cleanup NADs in terminating namespaces without pods#3102
kyrtapz wants to merge 1 commit into
openshift:release-4.20from
kyrtapz:cudn_ns_cleanup_fix

Conversation

@kyrtapz
Copy link
Copy Markdown
Contributor

@kyrtapz kyrtapz commented Mar 31, 2026

Skip namespaces with deletionTimestamp set when selecting target namespaces, triggering NAD deletion for terminating namespaces.

Manual, clean cherry-pick.
(cherry picked from commit 7606fd8)

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 31, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: f8254439-fe33-4270-b4b9-ab35089ad4fb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

.coderabbit.yml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'paths_ignore'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@kyrtapz kyrtapz changed the title CUDN: cleanup NADs in terminating namespaces without pods OCPBUGS-81484: CUDN: cleanup NADs in terminating namespaces without pods Mar 31, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-81484, which is invalid:

  • expected the bug to target the "4.20.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-81484 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Skip namespaces with deletionTimestamp set when selecting target namespaces, triggering NAD deletion for terminating namespaces.

(cherry picked from commit a61b7457eff1bbda01a91ec268a6c90221b9e54a)

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@kyrtapz kyrtapz changed the title OCPBUGS-81484: CUDN: cleanup NADs in terminating namespaces without pods [release-4.20] OCPBUGS-81484: CUDN: cleanup NADs in terminating namespaces without pods Mar 31, 2026
@kyrtapz
Copy link
Copy Markdown
Contributor Author

kyrtapz commented Mar 31, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-81484, which is invalid:

  • expected the bug to target the "4.20.z" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@kyrtapz
Copy link
Copy Markdown
Contributor Author

kyrtapz commented Mar 31, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-81484, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-81485 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-81485 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents
Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Skip namespaces with deletionTimestamp set when selecting target
namespaces, triggering NAD deletion for terminating namespaces.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
(cherry picked from commit 7606fd8)
@kyrtapz kyrtapz force-pushed the cudn_ns_cleanup_fix branch from 25f00e9 to 20b802c Compare March 31, 2026 11:15
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-81484, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-81485 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-81485 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents
Details

In response to this:

Skip namespaces with deletionTimestamp set when selecting target namespaces, triggering NAD deletion for terminating namespaces.

Manual, clean cherry-pick.
(cherry picked from commit 7606fd8)

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@kyrtapz
Copy link
Copy Markdown
Contributor Author

kyrtapz commented Mar 31, 2026

/hold
we need to wait for #3087 to land in 4.21

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 31, 2026
@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 31, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, pliurh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Apr 1, 2026

/retest-required

2 similar comments
@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Apr 1, 2026

/retest-required

@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@kyrtapz
Copy link
Copy Markdown
Contributor Author

kyrtapz commented Apr 27, 2026

/verified by @kyrtapz

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kyrtapz: This PR has been marked as verified by @kyrtapz.

Details

In response to this:

/verified by @kyrtapz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8e88264 and 2 for PR HEAD 20b802c in total

@arkadeepsen
Copy link
Copy Markdown
Member

/retest

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

2 similar comments
@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@jluhrsen
Copy link
Copy Markdown
Contributor

jluhrsen commented May 4, 2026

/retest-required

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

4 similar comments
@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@arkadeepsen
Copy link
Copy Markdown
Member

/test images

@arkadeepsen
Copy link
Copy Markdown
Member

/payload 4.20 ci blocking
/payload 4.20 nightly blocking

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 6, 2026

@arkadeepsen: trigger 5 job(s) of type blocking for the ci release of OCP 4.20

  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9e511d90-4930-11f1-9368-47fc29118ec5-0

trigger 9 job(s) of type blocking for the nightly release of OCP 4.20

  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-serial-1of2
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-serial-2of2
  • periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-upgrade-fips
  • periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9e511d90-4930-11f1-9368-47fc29118ec5-1

@arkadeepsen
Copy link
Copy Markdown
Member

/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

@arkadeepsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/34a416f0-49c5-11f1-896f-ae09686ac0d8-0

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a43b61 and 1 for PR HEAD 20b802c in total

@arkadeepsen
Copy link
Copy Markdown
Member

/hold

Waiting on #3070 to go in first

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@kyrtapz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 20b802c link false /test security

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@arkadeepsen
Copy link
Copy Markdown
Member

/hold cancel

#3070 is now merged

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2026
@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 07828af and 0 for PR HEAD 20b802c in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/hold

Revision 20b802c was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2026
@arkadeepsen
Copy link
Copy Markdown
Member

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2026
@arkadeepsen
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-edge-zones

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 07828af and 2 for PR HEAD 20b802c in total

@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.